Add support for Visual Studio 2026#2509
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (2)
WalkthroughAdded Visual Studio 2026 support across CI, build tooling, and ACE configuration: new CI matrix entries, new MSVC 14.5 config header and gating, VS2026 MakeProjectCreator feature and nmake files, and a NEWS entry documenting the addition. ChangesVS2026 support (CI, MSVC config, MakeProjectCreator, docs)
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Have you done a full build with tests? On github CI we only compile a small part of the code and don't run tests at all. |
|
Hi. Sorry, is there any documentation on building ACE and TAO? I can't find it. |
|
See https://htmlpreview.github.io/?https://github.com/DOCGroup/ACE_TAO/blob/master/ACE/ACE-INSTALL.html, at the bottom there are some instructions to build from git. Without a full build/test I think it is too early to say Visual Studio 2026 is supported, maybe it compiles the core, but the real test is a full build/test and also look at warnings and runtime test results. |
|
Depends on DOCGroup/MPC#242 |
|
Okay, Seems good. |
| feature(ace_languagestandard2017) { | ||
| specific(vs2017,vs2019,vs2022) { | ||
| specific(vs2017,vs2019,vs2022,vs2026) { | ||
| LanguageStandard = stdcpp17 |
There was a problem hiding this comment.
Don't think vs2026 needs this overwritten standard version
There was a problem hiding this comment.
CI tests in DOCGroup/MPC#242 failed because this option was missing. Will merging the PR with this option removed solve the problem?
There was a problem hiding this comment.
The default C++ version for Visual Studio 2026 is C++20 as far as I can determine from public documentation, so something to investigate and test more.
|
|
||
| feature(ace_languagestandard2017) { | ||
| specific(nmake) { | ||
| compile_flags += /std:c++17 |
There was a problem hiding this comment.
think this feature is not necessary
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
Summary by CodeRabbit
New Features
Chores
Documentation